* feat: route allowlisted Core-market supplies through funkit checkout

Adds a funkit checkout path for USDC/USDT/WBTC/cbBTC supplies on the Core
mainnet market, mirroring the production Polymarket integration:

- FunkitCheckout: ssr:false modal host in _app (next to the app's other
  modal hosts), single useFunkitCheckout instance, per-asset configs via
  beginCheckout(configOverride). Honors the SDK's onLoginFinished resume
  contract by replaying it once ConnectKit connects.
- funSupplyBridge: module-level imperative bridge across the client-only
  island boundary; clicks before the chunk loads fall back to the native
  supply modal.
- funSupplyAssets: allowlist holds only what live reserve data can't
  provide (real on-chain aToken symbols — wallet_watchAsset validates
  against the contract — and absolute icon URLs for EIP-747). Everything
  else (symbol, decimals, addresses, pool) comes from the clicked
  reserve + current market store. Gated on CustomMarket.proto_mainnet_v3
  so Prime/EtherFi reserves of the same underlyings stay native.
- funkitPreflight.css: scoped, zero-specificity slice of Tailwind
  preflight under [data-rk] — @funkit/connect relies on host preflight
  for form-control font inheritance and img max-width (its production
  hosts are Tailwind apps; this one isn't).
- patches/@Funkit+connect: React 18 forwardRef shim for funkit's
  React 19 ref-as-prop components, applied via patch-package.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat: always show fun-routed assets in supply list regardless of balance

fun checkout lets users supply from any EVM asset or fiat, so an empty
wallet must not hide the row or disable the Supply button for allowlisted
Core-market assets:

- SupplyAssetsList dust filter: fun-routed reserves always pass
- SupplyAssetsListItem / SupplyAssetsListMobileItem: zero wallet balance
  no longer disables Supply for fun-routed reserves (protocol-level
  blocks - inactive/frozen/paused/capped - still apply)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* test: pin FUN_SUPPLY_ASSETS aToken symbols to the address-book tokenlist

The catalog hardcodes receipt-token symbols (dashboard reserve data only
carries aTokenAddress; importing the 352KB/895-entry tokenlist at runtime
for 4 strings is a bad bundle trade). This test imports the tokenlist
where bundle size doesn't matter and fails CI if an address-book bump or
catalog typo ever disagrees - wallets validate wallet_watchAsset symbols
against the contract, so drift breaks the add-to-wallet flow.

Loaded via a node subprocess: the package's CJS tokenlist artifact is
data-less (its only module.exports is esbuild's dead-code annotation)
and next/jest forbids transforming node_modules, so neither artifact is
importable in-process under jest.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* refactor: source funkit receipt-token data from app state

The @aave/react SDK migration means useAppDataContext().supplyReserves
already carries each reserve's aToken Currency (address, symbol, decimals,
imageUrl) - the same state AddTokenDropdown renders on reserve-overview.
Look it up at the Supply click instead of keeping integrator-owned copies:

- FUN_SUPPLY_ASSETS catalog (hardcoded aToken symbols + icon URLs) shrinks
  to FUN_SUPPLY_UNDERLYINGS, a 4-address allowlist Set - purely the
  product decision of which assets route through fun checkout
- useSupplyButtonAction resolves the SDK reserve and threads
  aToken/underlyingToken metadata through the bridge; falls back to the
  native modal if SDK market data isn't loaded yet
- receipt icon improves: actual aToken artwork from aToken.imageUrl
  instead of reusing the underlying's icon
- deletes the address-book drift test (nothing hardcoded left to drift)
  and its node-subprocess workaround for the tokenlist's broken CJS
  artifact; drops the decimals/aTokenAddress threading from list items
- removes stray console.log debug block in SupplyAssetsListItemMobile

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* feat: register the ringed aToken icon via fun checkout add-to-wallet

The native flow's wallet icon is generated, not hosted: Base64Token wraps
the underlying's local SVG in Aave's gradient TokenRing and base64-encodes
it (Success.tsx / AddTokenDropdown). The SDK's aToken.imageUrl points at a
plain third-party logo (token-logos.family.co), so the fun checkout's
add-to-wallet icon didn't match.

Per-row generation, mirroring AddTokenDropdown: fun-routed supply rows
mount a hidden Base64Token via the shared useFunSupplyATokenIcon hook and
pass the data URI through the click payload - explicit data flow, ready at
row mount, never delays beginCheckout. Hosted imageUrl stays as the
fallback for a click that beats generation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: drop unused tronweb dependency

tronweb isn't a @funkit/connect dependency or peer, isn't referenced in
its bundle, and nothing in this repo imports it - a leftover from early
integration setup. Its exact bignumber.js@9.1.2 pin hoisted over the
repo's ^9.0.2 -> 9.3.1 resolution, hiding the UMD global type that
upstream's PriceInput.tsx relies on post-rebase.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

tronweb is a peerDependency of @relayprotocol/relay-tron-wallet-adapter,
statically imported via @funkit/connect -> @funkit/fun-relay. pnpm
auto-installs peers (why funkit's monorepo never trips on it); yarn v1
doesn't, so the host must declare it - removing it broke `next build`
with "Module not found: Can't resolve 'tronweb'".

Its exact bignumber.js@9.1.2 pin used to hoist over the repo's
^9.0.2 -> 9.3.x resolution, hiding the BigNumber UMD global type that
PriceInput.tsx relies on. Solved via the repo's existing resolutions
block: "bignumber.js": "^9.3.1" collapses all ranges to one 9.3.1 copy.

Verified with a full `next build` (clean compile, 17/17 pages).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Bump @funkit/connect 9.18.0 -> 9.19.0, and its hard deps to match
(@funkit/api-base 4.4.1 -> 4.5.0, @funkit/chains 1.2.0 -> 2.0.0).

9.19.0 ships PaddedScrollableArea as forwardRef natively, so the React
18 compatibility patch is no longer needed -- drop
patches/@Funkit+connect+9.18.0.patch. The native-flow toggle now always
shows (runtime behavior in the new build, no code change required).

Verified: all SDK exports the app uses still exist, buildFunSupplyConfig
matches AaveSupplyCheckoutInput, single deduped chains resolution, and
tsc --noEmit passes clean.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Addresses @sammdec's review comments. The patch-package patch is gone (SDK
bumped to @funkit/connect 9.19.0, which ships the PaddedScrollableArea
forwardRef fix natively) and .nvmrc now requires node 20.19, so the
supporting scaffolding is dead:

- delete .yarnrc (ignore-engines) — node 20.19 satisfies @solana/addresses' >=20.18
- package.json: drop the "postinstall": "patch-package" script + patch-package devDep
- .prettierignore: drop the *.patch and .yarnrc entries
- .gitignore: revert *.tsbuildinfo -> tsconfig.tsbuildinfo (matches upstream)
- regenerate yarn.lock (patch-package removed)

yarn install verified clean on node 20.19 with .yarnrc removed (no engines error).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…6) (#3)

The demo-key fallback was the only use of @funkit/api-base; the funkit
API key now comes solely from NEXT_PUBLIC_FUNKIT_API_KEY. The package
remains a pinned transitive dep of @funkit/connect, so no resolved
versions change.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>